Open
Bug 718205
Opened 13 years ago
Updated 3 years ago
Investigate catching uncaught JS exceptions through window.onerror in iframes (or child windows) of (plain) mochitests
Categories
(Testing :: Mochitest, defect)
Testing
Mochitest
Tracking
(Not tracked)
NEW
People
(Reporter: sgautherie, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: autotest-issue)
This is a follow-up to bug 652494 and bug 703176.
1- Mark (various) noticed cases as dependent.
2- Try to investigate and find a solution if possible.
Reporter | ||
Updated•13 years ago
|
Summary: Some plain mochitests still not failing when uncaught JS exceptions occur → Investigate catching uncaught JS exceptions through window.onerror in iframes of plain mochitests
Reporter | ||
Comment 1•13 years ago
|
||
Iirc, I initially filed this bug for plain mochitests only as a first step:
the assumption was +/- that plain tests should "never" cause exceptions,
whereas we might need to deal with "expected" exceptions in some (browser-)chrome tests.
Anyway, the first part should be to at least catch and report these/all exceptions as warnings.
Then we can decide how to proceed from there.
Blocks: 702678
Keywords: autotest-issue
Summary: Investigate catching uncaught JS exceptions through window.onerror in iframes of plain mochitests → Investigate catching uncaught JS exceptions through window.onerror in iframes (or child windows) of (plain) mochitests
Reporter | ||
Comment 2•13 years ago
|
||
Ftr, targeted exceptions are ones that show up in the Error Console (as uncaught), but that our SimpleTest harness doesn't currently see/catch.
Assignee | ||
Updated•7 years ago
|
Component: BrowserTest → Mochitest
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•